home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group96a.txt
/
000176_icon-group-sender _Wed Aug 7 16:35:33 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-09-05
|
1KB
Received: by cheltenham.cs.arizona.edu; Thu, 8 Aug 1996 08:31:37 MST
Date: Wed, 7 Aug 1996 16:35:33 -0500
Message-Id: <199608072135.QAA03282@ns1.computek.net>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: gep2@computek.net
Subject: Re: dos system call
To: icon-group@cs.arizona.edu
X-Mailer: SPRY Mail Version: 04.00.06.17
Errors-To: icon-group-errors@cs.arizona.edu
Status: O
>The system() call has another effect in DOS which is unfortunate:
it calls up another copy of COMMAND.COM, meaning you've lost another
64K of critical memory in addition to the process you are trying
to start.
Actually, no. If you bring up the MEM /C command you'll see that COMMAND.COM
takes up a LOT less than 64K... on one of my machines here, COMMAND.COM actually
uses 4.736 bytes of conventional (and no upper) memory. So it uses some memory
for the extra command shell, but nowhere near 64K worth.
>Most DOS C compilers have other ways (exec..) that do not invoke an addition
COMMAND.COM, but this may again be C-compiler dependent.
That's another option too, although generally that option doesn't let you bring
up batch files or shell internal commands, and also generally doesn't search the
path for the executable. At least that's typical behavior on MS-DOS systems.
Gordon Peterson
http://www.computek.net/public/gep2/